Skip to content

Conversation

rosieyohannan
Copy link
Contributor

@rosieyohannan rosieyohannan commented Sep 29, 2025

Description

Update to sections that mention active or unregistered users to be correct with pricing model

Reasons

Why did you make these changes?

Content Checklist

Please follow our style when contributing to CircleCI docs. Our style guide is here: https://circleci.com/docs/style/style-guide-overview.

Please take a moment to check through the following items when submitting your PR (this is just a guide so will not be relevant for all PRs):

  • Break up walls of text by adding paragraph breaks.
  • Consider if the content could benefit from more structure, such as lists or tables, to make it easier to consume.
  • Keep the title between 20 and 70 characters.
  • Consider whether the content would benefit from more subsections (h2-h6 headings) to make it easier to consume.
  • Check all headings h1-h6 are in sentence case (only first letter is capitalized).
  • Include relevant backlinks to other CircleCI docs/pages.

@rosieyohannan rosieyohannan requested review from a team as code owners September 29, 2025 08:19
:experimental:

It is possible for _unregistered_ users to trigger pipelines, and therefore, spend credits. Use the **Prevent unregistered user spend** option to only allow registered users the ability to trigger work that consumes credits. For a full breakdown of the various ways pipelines can be triggered, see the xref:orchestrate:triggers-overview.adoc[Triggers overview].
Unregistered users trigger pipelines, spend credits and count towards your plan usage. You can choose to use the **Prevent unregistered user spend** option to only allow registered (users with a CircleCI account) users the ability to trigger work that consumes credits. For a full breakdown of the various ways pipelines can be triggered, see the xref:orchestrate:triggers-overview.adoc[Triggers overview].
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nathanfishcircleci main change here

Docker layer caching (DLC) reduces build times on pipelines where Docker images are built by only rebuilding Docker layers that have changed (read more on the xref:guides:optimize:docker-layer-caching.adoc[Docker Layer Caching] page). DLC costs 200 credits per job run.

To estimate your DLC cost, look at the jobs in your config file with Docker layer caching enabled, and the number of Docker images you are building in those jobs. There are cases where a job can be written once in a config file but the job runs multiple times in a pipeline, for example, with parallelism enabled.
To estimate your DLC cost, look at the jobs in your config file with Docker layer caching enabled, and the number of Docker images you are building in those jobs. It is possible for a job to appear once in a config file but the job runs multiple times in a pipeline, for example, with parallelism enabled.
Copy link
Contributor

@yaningo yaningo Sep 30, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The sentence:

It is possible for a job to appear once in a config file but the job runs multiple times in a pipeline, for example, with parallelism enabled.

sounds "weird" (for lack of a better word).

Could we reword it? Something like:

In some cases, a job that appears only once in a config file can run multiple times in a pipeline. For example, with parallelism enabled.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ooo yes thanks for fixing that weirdness!

@rosieyohannan rosieyohannan requested a review from a team as a code owner September 30, 2025 14:00
Copy link
Contributor

@nathanfishcircleci nathanfishcircleci left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great.

@rosieyohannan rosieyohannan merged commit 23d54ee into main Oct 1, 2025
3 checks passed
@rosieyohannan rosieyohannan deleted the DOCSS-1930-unregistered-users branch October 1, 2025 12:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants